Skip to content

Conversation

@vincentsarago
Copy link
Member

This PR adds a /maps endpoint which follow the OGC Maps API spec

The main issue is that we need to enable preview for collection/search which will be super expensive/slow operation. In this PR I choose to use collection extent footprint to create the preview

**layer_params.as_dict(),
**dataset_params.as_dict(),
**assets_accessor_params.as_dict(),
)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use

A Content-Attribution: header SHOULD be included in the response to a map request to indicate any attribution relevant to the data being returned, especially if this attribution varies based on the subset and scale of the request.

when returning the full image created with https://www.naturalearthdata.com/downloads/10m-raster-data/10m-natural-earth-2/

add_statistics=True,
add_viewer=True,
add_part=True,
add_ogc_maps=True,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory we could add https://docs.ogc.org/is/20-058/20-058.html#conf_collection-map to the conformance link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant